Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 17:03
    paul commented #32
  • 16:44
    paul commented #32
  • 10:56
    solnic commented #32
  • 10:30
    solnic commented #32
  • Dec 05 09:29

    solnic on master

    Clear exception message when an… Add gem names to plugins Merge pull request #128 from sk… (compare)

  • Dec 05 09:29
    solnic closed #128
  • Dec 05 09:29
    solnic closed #127
  • Dec 04 18:49
    micahphone starred dry-rb/dry-monads
  • Dec 04 17:43
    icy-arctic-fox starred dry-rb/dry-types
  • Dec 02 12:37
    pedrofurtado starred dry-rb/dry-view
  • Dec 02 11:59
    lenon starred dry-rb/dry-monads
  • Dec 01 11:06

    flash-gordon on declare-finalized

    (compare)

  • Dec 01 11:06

    flash-gordon on master

    Set initial value for ivar Merge pull request #131 from dr… (compare)

  • Dec 01 11:06
    flash-gordon closed #131
  • Dec 01 11:05
    flash-gordon opened #131
  • Dec 01 11:03

    flash-gordon on declare-finalized

    Set initial value for ivar (compare)

  • Nov 30 16:50
    paul commented #32
  • Nov 30 16:50
    paul synchronize #32
  • Nov 30 16:44
    paul synchronize #32
Nikita Shilnikov
@flash-gordon
exactly my case
Christian Georgii
@cgeorgii
Hey @flash-gordon, not sure if you had the chance to check this dry-rb/dry-types#277 out? I think we're just waiting for your input. No hurry, though, just don't want the momentum to get lost.
Nikita Shilnikov
@flash-gordon
on my list, working on dry-configurable atm
Christian Georgii
@cgeorgii
Ok, thanks for letting me know ;)
Kumayl Nazary
@knazary
Hey @timriley, appreciate you guiding me here!
I'm working at a company and we've been building an API to replace our legacy java platform.. everything has been going well in the past year up until very recently. Our ruby application (the api) is dockerized and deployed to AWS' Elastic Container Service.
However, after the latest changes, when I try to deploy (building and publishing via docker), on the bundle install step (from my dockerfile), I receive this error: `fatal: Could not parse object '#{some long hash}'.
Any idea how I could fix this? @timriley @solnic
Tim Riley
@timriley
@knazary there’s not enough information to help you here, and the error could be coming from anything, really, not necessarily anything to do with dry-rb.
@knazary Also, we cannot provide support related to application deployment. This is outside our purview as gem developers.
Kumayl Nazary
@knazary
This happened ever since the rodakase repo was archived. I think there may have been specific commits removed?
got it.
Tim Riley
@timriley
@knazary yeah, maybe some commits disappeared. You should 100% no longer be using rodakase. That project was converted to dry-web, dry-system, dry-view a long time ago.
Piotr Solnica
@solnic
:point_up_2:
Tim Riley
@timriley
Rodakase was also very clearly a bleeding edge/experimental project, we didn’t get anywhere even close to guaranteeing stability there
Kumayl Nazary
@knazary
Guys, you are the geniuses. I'm a 25 year old mediocre developer struggling with legacy code here :D
Tim Riley
@timriley
I would definitely encourage you move off that and onto the corresponding dry-rb gems.
In the meantime, perhaps there’s a checked out copy of that commit in your local bundle cache
Kumayl Nazary
@knazary
haha, thanks for pointing me towards the real solution though
Piotr Solnica
@solnic
:point_up_2: ^2 :smile:
Tim Riley
@timriley
you might be able to save yourself by finding that and pushing it up to your own repo
However, do NOT let that prevent you from doing the right thing and getting off that repo ASAP
Kumayl Nazary
@knazary
Got it. This was great. In relation to my local bundle cache, which file(s)/directory would be the right one to push to a repo of my own?
Tim Riley
@timriley
If it’s a git repo clone, you want to push the whole thing up
Kumayl Nazary
@knazary
image.png
Tim Riley
@timriley
¯_(ツ)_/¯
Just find a working local cached copy, if you can, push it up, then point your Gemfile to that repo’s master
I have no idea if this will work, but it’s something
It’s late here and I don’t have the time to look into bundler’s internals right now so unfortunately I can’t help further
Nikita Shilnikov
@flash-gordon
I would check out bundler
Kumayl Nazary
@knazary
Thanks a bunch @timriley ! Will try this workaround for now. And next up will be a real upgrade.
Nikita Shilnikov
@flash-gordon
since it's a git-source dep it must be managed by bundler, not rubygems
Kumayl Nazary
@knazary
@flash-gordon could you expand/elaborate on what you mean?
Tim Riley
@timriley
Go into your (hopefully working) local checkout of the app
type bundle show rodakase
that will show you where bundler has checked out the copy of the gem
Kumayl Nazary
@knazary
probably because i'm using rbenv
image.png
ah found it.. that was cuz i removed my gemfile.lock
image.png
Nikita Shilnikov
@flash-gordon
okay then you can re-push it wherever you like and update your gemfile after that
Kumayl Nazary
@knazary
Gonna try now -- appreciate you both @flash-gordon @timriley
Marwan Rabbâa
@waghanza
hi
I've met a hanami failure with the last dry-logic
has anyome meet this issue ?
Nikita Shilnikov
@flash-gordon
yes, you can pin it to ~> 0.4.2, we also released dry-validation 0.12.3 which has this dependency, unfortunately, I'm afraid hanami depends on an older version of dry-validation
Marwan Rabbâa
@waghanza
ok. course I've pined version for my benchmark
Marwan Rabbâa
@waghanza
however, I see that hanami-validation is pined to dry-validation 0.11.x
https://github.com/hanami/validations/blob/v1.3.1/hanami-validations.gemspec#L22