Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 12:11
    solnic labeled #66
  • 12:11
    solnic labeled #66
  • 12:10
    solnic opened #66
  • 12:10
    solnic labeled #68
  • 12:10
    solnic labeled #68
  • 12:10
    GustavoCaso opened #68
  • 12:09
    solnic labeled #390
  • 12:09
    solnic labeled #390
  • 12:09
    patrickclery opened #390
  • Jan 26 22:33
    Travis dry-rb/dry-view (master) errored (712)
  • Jan 26 22:30

    dry-bot on master

    [devtools] sync (compare)

  • Jan 26 22:30

    dry-bot on master

    [devtools] sync (compare)

  • Jan 26 22:30

    dry-bot on master

    [devtools] sync (compare)

  • Jan 26 22:30

    dry-bot on master

    [devtools] sync (compare)

  • Jan 26 22:30

    dry-bot on master

    [devtools] sync (compare)

  • Jan 26 22:30

    dry-bot on master

    [devtools] sync (compare)

  • Jan 26 22:30

    dry-bot on master

    [devtools] sync (compare)

  • Jan 26 22:30

    dry-bot on master

    [devtools] sync (compare)

  • Jan 26 22:30

    dry-bot on master

    [devtools] sync (compare)

  • Jan 26 22:30

    dry-bot on master

    [devtools] sync (compare)

Tim Riley
@timriley
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
Piotr Solnica
@solnic
hey folks, I've finally finished first version of dry-schema and it was pushed to rubygems today. Rough docs are here https://dry-rb.org/gems/dry-schema/ (heavily based on current dry-validation docs). Feel free to test it out and let me know how it goes. I'll be publishing a blog post about this release later this week or after Feb 11. Anyhow, check out the docs, gem i dry-schema and have fun. This also means that I'll start working on dry-validation 1.0.0 in February.
Vasily Kolesnikov
@v-kolesnikov
:tada:
I'll test it soon.
Piotr Solnica
@solnic
btw it is possible to have both dry-validation and schema installed (FWIW)
Christopher Swasey
@endash
Good timing. I was just looking at both this week and was confused that -schema didn't seen to exist yet.
Pablo Crivella
@pablocrivella
Question: On a rails app, would it be recommended to define my DI Container on an initializer?Currently i don't have it there, but idk if there could be some issues with that
Piotr Solnica
@solnic
@pablocrivella yes this should work well, I've done that in the past and had no problems with such a setup
Pablo Crivella
@pablocrivella
I was having some issues when combined with dry-auto_inject tho
That were fixed by moving the Container to an initializer, but maybe the issue was something else?
Kumayl Nazary
@knazary
@timriley @flash-gordon just wanted to thank you both for your workaround suggestions from the other day. Finding the checked out copy of the missing commits in my local bundle cache and pushing to a repo of my own did the job :pray:
@pablocrivella code reloading in rails may get in your way. so be aware of that
Nikita Shilnikov
@flash-gordon
rails way vs your way
@knazary glad to hear that
Pablo Crivella
@pablocrivella
What would be a better approach when using dry-container for testing? Should i stub and unstub per example? or stub everything and unstub where needed? I couldn’t find an unstub_all method