Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jul 25 21:06
    limpid-kzonix starred monix/monix-connect
  • Jul 22 12:48
    scala-steward opened #706
  • Jul 17 10:25
    scala-steward synchronize #705
  • Jul 17 10:25
    scala-steward synchronize #700
  • Jul 17 10:25
    scala-steward synchronize #674
  • Jul 17 10:06

    paualarco on master

    Update s3, sqs to 2.16.93 (#687) (compare)

  • Jul 17 10:06
    paualarco closed #687
  • Jul 17 10:06

    paualarco on master

    Update google-cloud-nio to 0.12… (compare)

  • Jul 17 10:06
    paualarco closed #688
  • Jul 17 10:06

    paualarco on master

    Update scala-collection-compat … (compare)

  • Jul 17 10:06
    paualarco closed #694
  • Jul 17 10:05
    paualarco closed #702
  • Jul 17 10:05

    paualarco on master

    Update lettuce-core to 6.1.4.RE… (compare)

  • Jul 16 20:31
    scala-steward closed #704
  • Jul 16 20:31
    scala-steward opened #705
  • Jul 15 20:23
    scala-steward closed #703
  • Jul 15 20:23
    scala-steward opened #704
  • Jul 14 20:38
    scala-steward closed #697
  • Jul 14 20:38
    scala-steward opened #703
  • Jul 14 12:38
    scala-steward closed #679
Pau Alarcón
@paualarco
First PR! Removed references to cloriko and added sbt configurations (more info in the description).
Pau Alarcón
@paualarco
I am afraid I have no access to merge the reviewed PR 😯
Piotr Gawryś
@Avasil
Weird
try now @paualarco
Pau Alarcón
@paualarco
thank you @Avasil
Alexandru Nedelcu
@alexandru
@paualarco sorry, forgot to double check your permissions on that repo, I've made you admin on the monix-connect project
Pau Alarcón
@paualarco
No worries! thanks @alexandru
Pau Alarcón
@paualarco
I have created some issues and linked the to a milestone. See project status here: https://github.com/monix/monix-connect/projects/1
My changes to the alpakka AvroParquet connector were gladly accepted, in which it still have the constrain of only writing to parquet from Avro
Whereas the one in Monix Connect does not, that's why it is only called Parquet :)
Alexandru Nedelcu
@alexandru
Nice
Pau Alarcón
@paualarco
Hello guys! All the connectors have been refined and test coverage has been improved as well!
Still might be things to clean up yet, but I feel confident on start publishing the next software increments as well as getting used to the release process.
The documentation will still clearly indicating that the project is not yet stable.
What do you think? In case you do not have inconveniences it would be great to get some guidance on how to do so...
At the same time I could start migrating the documentation to a web version.
Piotr Gawryś
@Avasil
I can help with release, I don't remember initial setup (I think it is required to create a ticket somewhere to get Sonatype access to monix namespace?) but I should have old notes somewhere :D
Piotr Gawryś
@Avasil
I aggre it's a good idea to release 0.1.0, it can still be useful to people and it's a chance to get feedback. Consider setting up Mima and try to preserve bincompat in 0.1.x to get used to it but also not worry about upgrading to 0.2.0 soon. Treat it like an exercise until the project fully stabilizes.
Pau Alarcón
@paualarco
Sounds good! :) Okay will have that in mind, there is no rush indeed. Some feedback would be appreciated since now people can't even play with it.
Alexandru Nedelcu
@alexandru
We should grant @paualarco access for publishing on Sonatype for io.monix and let him be in charge of the release, to get accustomed to the process.
I don't remember exactly the procedure, but I think we should open a ticket on Sonatype or reuse an old one.
We have this issue on Sonatype, we could add a comment to it: https://issues.sonatype.org/browse/MVNCENTRAL-2890
@paualarco let me know your Sonatype username
Or create an account if you don't have one
And yes, publishing a 0.1.0 sounds like a good plan. Let it mature a little before declaring 1.0.0, because afterwards you have to worry about compatibility.
Pau Alarcón
@paualarco
Hey @alexandru, I've just created an account with username paualarco, but I can't access to the ticket link you sent.
And yes, that's the plan, to stay in 0.x for a while until being confident enough. Eventually I would notify the future intentions before hand in order to get your approval / opinion.
Alexandru Nedelcu
@alexandru
@paualarco no worries, I've made the request, will let you know when an admin at Sonatype replies
Alexandru Nedelcu
@alexandru
@paualarco got a confirmation, you can now publish on Sonatype under the io.monix organization
let us know if you need help setting things up, Sonatype is a challenge
I recomment that you setup an automated deployment process via GitHub Actions
My template might provide some help in setting that up: https://github.com/alexandru/typelevel-library.g8
It's basically making use of this plugin: https://github.com/olafurpg/sbt-ci-release
Pau Alarcón
@paualarco
It will be interesting :)
Pleas let me know once the people from Sonatype have replied and given me the access.
Is web documentation something I have to worry about now? Or will be later?
I would probably come up with more questions later on :P
Alexandru Nedelcu
@alexandru
@paualarco you should already have access with your user
Worry about documentation later.
Also the first release could be a "hash release"
If you setup sbt-ci-release, it will also include: https://github.com/dwijnand/sbt-dynver
And this nice plugin can generate dynamic versions for you, so instead of publishing a 0.1.0-SNAPSHOT, you could publish something like 0.1.0-c93fa3
Where c93fa3 is the git SHA
So try publishing such a version from your localhost and see if it works
Pau Alarcón
@paualarco
Cool will go through the repos you mentioned and try to do so
You are also using github4s, aren't you?
Pau Alarcón
@paualarco
What are the reasons I should migrate travis to github actions? https://github.com/olafurpg/sbt-ci-release is using travis.
Alexandru Nedelcu
@alexandru

You are also using github4s, aren't you?

It's used by the documentation website, you can ignore that.

What are the reasons I should migrate travis to github actions? https://github.com/olafurpg/sbt-ci-release is using travis.

There are pros and cons. If you want, stay with Travis. One thing that bothers me and why I want to migrate main Monix to to GH Actions is that Travis is slow. And GH Actions is right there, no need to do anything extra.

On the other hand w/ Travis you can quickly setup a build matrix, whereas in GH Actions it might take some work depending on complexity.

Pau Alarcón
@paualarco
@alexandru followed your recommendations on moving to GitHub workflow, and it is really much better now! :)
I've deployed the first snapshot :D
If you see something wrong on that configuration please do point it out
Pau Alarcón
@paualarco
Maybe I ve exagerated a bit saying much better haha but at the end I prefered now too
Pau Alarcón
@paualarco
mmmh, the project name looks familiar XD
Piotr Gawryś
@Avasil
Probably inspired by Kafka Connect but who knows