Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • May 21 08:40

    mergify[bot] on master

    Update cats-effect to 3.3.12 Merge pull request #734 from sc… (compare)

  • May 21 08:40
    mergify[bot] closed #734
  • May 21 08:34
    scala-steward opened #734
  • May 20 02:17

    mergify[bot] on master

    Update circe-core, circe-generi… Merge pull request #733 from sc… (compare)

  • May 20 02:17
    mergify[bot] closed #733
  • May 20 02:12
    scala-steward opened #733
  • May 14 10:30
    scala-steward opened #732
  • Apr 30 10:34

    mergify[bot] on master

    Update scalafmt-core to 3.5.2 Merge pull request #731 from sc… (compare)

  • Apr 30 10:34
    mergify[bot] closed #731
  • Apr 30 10:29
    scala-steward opened #731
  • Apr 25 11:43

    mergify[bot] on master

    Update sbt-tpolecat to 0.3.1 Merge pull request #730 from sc… (compare)

  • Apr 25 11:43
    mergify[bot] closed #730
  • Apr 25 11:37
    scala-steward opened #730
  • Apr 25 04:50

    mergify[bot] on master

    Update scalatest to 3.2.12 Merge pull request #729 from sc… (compare)

  • Apr 25 04:50
    mergify[bot] closed #729
  • Apr 25 04:44
    scala-steward opened #729
  • Apr 22 18:42

    mergify[bot] on master

    Update sbt-tpolecat to 0.3.0 Merge pull request #728 from sc… (compare)

  • Apr 22 18:42
    mergify[bot] closed #728
  • Apr 22 18:37
    scala-steward opened #728
  • Apr 21 13:29

    mergify[bot] on master

    Update sbt-header to 5.7.0 Merge pull request #727 from sc… (compare)

Victor Viale
@Koroeskohr
ahhhh sbt-revolver that's the thing I forgot about
thank you Gavin!
Victor Viale
@Koroeskohr
as a slightly off topic question, would you recommend RabbitMQ in Action as the book to read on the topic or do you have something else in mind?
Gavin Bisesi
@Daenyth
I haven't read it
I just learned from a live codebase + reading docs and api methods as needed
Gavin Bisesi
@Daenyth

merged the metrics pr

@gvolpe cut a release when you have time?

Gabriel Volpe
@gvolpe
Will do :+1: , thanks. In the meantime, people can try the published snapshot: fs2-rabbit_2.13-0.0.0+1-fa7deae1-SNAPSHOT
Saskia Gennrich
@pektinasen
Hey everyone. Can someone help me to create an SSLContext for TLS without certificate checking?
In python-pika it would be this setting: ssl_options = pika.SSLOptions(context = ssl.SSLContext(ssl.PROTOCOL_TLS))
I just cannot figure it out without supplying certificate stores and whatnot
Gavin Bisesi
@Daenyth
@pektinasen I don't have time right now, but I bet if you google for doing it in java, that's going to be how you do it
assuming we're using the standard SSLContext class
Saskia Gennrich
@pektinasen
I tried that. unfortunately without success
No problem. I'll google some more. I was converting this to scala:https://stackoverflow.com/a/19723687/1041722
but didn't work.
Saskia Gennrich
@pektinasen
seems to be something else. I'm pretty sure I have setup everything correctly now.
Saskia Gennrich
@pektinasen

I'm new to rabbitmq and fs2, so my questions might not directly related to fs2-rabbit, but rabbitmq in general. I'm consuming a queue I have no control over, is there a way to tell the queue I only want events that were generated after I created the connection.
I'm getting events from 2 days ago. Which is when I first started consuming events from this queue.
Sorry, for these basic questions.

Is this even something a consumer has control over?

Gavin Bisesi
@Daenyth
yes, ish
You can construct a non-durable queue that gets created on startup and deleted once your consumer disconnects
so it won't be "a queue", it would be "a new queue for each process"
Note that under that model if publishers publish when the consumer is down, the message would be discarded or go to whatever dead-letter routing you have
Gabriel Volpe
@gvolpe
@Daenyth if you need a new release, feel free to cut a new one whenever you need it, you should have the rights to do so. All you need to do is to tag a new version starting withv (e.g. v2.3.0) and write down the release notes. sbt-ci-release will do the rest.
Gavin Bisesi
@Daenyth
:+1: cool
catostrophe
@catostrophe
@Daenyth @gvolpe I just opened a PR to update deps to the latest versions (where Steward failed). Can we have a minor release soon?
Gabriel Volpe
@gvolpe
@catostrophe thanks a lot! Could you edit the description of the PR to link the PRs and Issues it closes? e.g. closes #35 and closes #64, etc
catostrophe
@catostrophe
Sure
Gabriel Volpe
@gvolpe
I already approved it but this would be nice to have so we don't have to come back to track what hasn't been closed / merged, much appreciated it
Note that as soon as the PR is merged, a new SNAPSHOT is published so you can already use that until a release is published
catostrophe
@catostrophe
I hope this works with PRs not only issues.
Gabriel Volpe
@gvolpe
If you're interested in becoming a maintainer, let me know. I'd be happy to grant you permissions
Yes, it works with PRs too
It's not a responsibility, you do whatever you can when you can, this is OSS :)
So for example, making a release would just be creating a new release (which creates a tag) and writing down the release notes
catostrophe
@catostrophe
Regarding becoming a maintainer, thanks, I will think.
And thanks for the quick reaction
Gabriel Volpe
@gvolpe
:+1:
Gabriel Volpe
@gvolpe

I cut a long overdue new release (sorry for the delay): https://github.com/profunktor/fs2-rabbit/releases/tag/v2.2.0

Thanks to everyone involved: @catostrophe @Daenyth @DougC @bpholt @kubum :tada:

Gavin Bisesi
@Daenyth
Awesome :)
Gabriel Volpe
@gvolpe
@Daenyth any objections to cut a new major release v2.3.0 to include @aywengo 's changes?
Gavin Bisesi
@Daenyth
Would be 3.0.0 I believe
but yeah, let's go for it
Gabriel Volpe
@gvolpe
Is that necessary, though? We only maintain a single branch anyway :grimacing:
Gavin Bisesi
@Daenyth
It's not a binary compatible update
if we want to say that we break bincompat in minor semver releases, then it can be 2.3.0. But the scala community is much more that minor keeps compat, major breaks it
I should get mima set up..
Gabriel Volpe
@gvolpe
I don't really mind, you're a real user so if 3.0.0 is preferable I'll go for it
Gavin Bisesi
@Daenyth
It is - it could actually cause us link errors since we have intermediate jars using fs2-rabbit
Hence my suggestion to hide the case class behind a builder-shaped trait
Gabriel Volpe
@gvolpe
What I don't understand is updating to 2.3.0 or 3.0.0 would cause the same issue if any
Gavin Bisesi
@Daenyth
Version number is meaningless - it's just a communication tool
Scala ecosystem generally tells us that minor version bumps are compatible, so someone could update one of the applications without realizing it would break things (and I don't necessarily trust everyone's code coverage ;) )